Integrators can provide a unique barcode pattern on a Generate request; this adds information to a barcode that is in addition to, not replacing, any barcode values submitted in the request containing an Barcode object as part of the AncillaryOutputOption.
In this method, you define a package rule that will contain custom data. The custom data, as a name/value pair, should use a naming convention of BRCD with the value being a string. The system them converts the custom data into a recognizable pattern (%BRCD%) and renders the data into the generated barcode in first position.
In this example, the custom data described above is associated with a request containing a Barcode object submitted with a Code128 barcode type and a pattern that included the %date% parameter. The generated barcode contains the custom data in first position followed by the date as requested as BRCD1 TestDoc1BRCD2 TestDoc108/18/2014. Where the two BRCD values represent custom data and 08/18/2014 represents the values from the %date% parameter.
